home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
CU Amiga Super CD-ROM 17
/
CU Amiga Magazine's Super CD-ROM 17 (1997)(EMAP Images)(GB)[!][issue 1997-12].iso
/
CUCD
/
Sound
/
MSE-DEMO
/
Readme.FAQ
< prev
next >
Wrap
Text File
|
1997-06-28
|
7KB
|
165 lines
MIDI SYStem EXplorer (Pre-Release)
FREQUENTLY ASKED QUESTIONS
v1.1
----------------------------------------------------------------------------
> Does MSE support all MIDI devices?
> I would LOVE to see support for Roland Super Jx-10, Jx-8p, Juno-1 and 2,
> Mks-50, Juno-106, and lot of other gear.
----------------------------------------------------------------------------
We have done our best to support most of the features that we have seen so
far. However, not everything can be controlled by MSE. It is possible to
make partial editors so if something has not been implemented yet, it can
be omitted and added later. There are 1000s of device MIDI
implementations, and we have not seen them all. Some things may not yet be
supported simply because we are not aware of them.
Currently, devices that require handshake communication are not supported.
Keep in mind that some devices support both handshake and one-way
communication so those may work.
We suggest that you send us a copy of the SYSEX docs for the units you want
to make modules for (check with us first to see if we already have the
info). We will have a look at the documentation and confirm that MSE
supports everything required by that unit. If it does not, we can try and
implement it at that time. That way, you do not have to spend your money
until the program meets your needs.
We are currently making, or have completed, the following modules:
Akai S612
Boss SE-50
Korg Wavestation
Oberheim Matrix-1000
Oberheim Matrix-6R
Roland A-50
Roland A-880
Roland Juno-106
Roland MKS-50
Roland MSE-1
Roland R8 / R8M
Roland S-550
Roland SDX-330
Roland SRV-330
Yamaha SPX-90II
Yamaha TX802
The following are also expected:
Blue Ribbon One Stop Music Shop
Emu Proteus
Korg 05DR
Peavey DPM-V3
Yamaha SY77
Yamaha TG-33
Yamaha TG-100
Yamaha YS-200
more as we find out about them...
----------------------------------------------------------------------------
> Is it possible to manage banks of sounds?
----------------------------------------------------------------------------
Currently, no. But it is in the plans. We are waiting to see how this is
implemented on more devices, so that we can design the definition language
changes accordingly.
----------------------------------------------------------------------------
> Does MSE coexist with Music-X?
----------------------------------------------------------------------------
We are trying to obtain the necessary information to better integrate MSE
with Music-X. If someone has this information and is willing to share it
with us, we will be happy to improve on this.
For now, you will have to disable use of the MIDI port by Music-X, while
using MSE.
We have learned that Music-X uses CAMD compatible drivers though it does
not actually use CAMD. We are looking further into this.
----------------------------------------------------------------------------
> Does MSE support the CAMD.library?
----------------------------------------------------------------------------
Yes! Currently MSE supports the CAMD.library, Midi.library and the
BlueRibbon.library (which allows simultaneous use with other software that
uses them). We will further improve on this support in future versions.
----------------------------------------------------------------------------
> Will MSE open on the Workbench screen?
----------------------------------------------------------------------------
YES! MSE can open on any public screen.
----------------------------------------------------------------------------
> MSE did not fill up my Multiscan 640x495 res screen.
----------------------------------------------------------------------------
NTSC 640x400 is the default screen size used by MSE. It can be changed
with a tooltype.
Note that modules included with the demo are all designed for 640x400
screens. Even if you change the screenmode, these modules will still have
windows defined for a 640x400 screen. However, this can be changed by
editing definition files and recompiling them with the compiler included
with the registered MSE. The MSE screen can open to any size supported by
your hardware.
----------------------------------------------------------------------------
> I would like to know more about what is involved in writing a driver.
> I am NOT a programmer! (But I am somewhat familiar with sysex as I have
> to use it so send various commands from time to time).
----------------------------------------------------------------------------
Hopefully, we have developed a 'definition language' that is simple enough
for almost anyone to use. Some knowledge of hexadecimal/binary number
systems would be of help, but may not be required. Much of this depends on
the MIDI documentation for your device. Some manufacturers have very easy
MIDI implementation, others have very cryptic and confusing methods.
We would be happy to help with SYSEX 'programming'. It is likely that once
we showed you how to implement a few parameters, you could probably finish
the rest on your own. If we have a copy of the SYSEX info, it would
certainly make things much easier for us to help you out.
----------------------------------------------------------------------------
> I would prefer more control over the program, like screenmode requester.
----------------------------------------------------------------------------
Screenmode, depth, etc are set with tooltypes. Currently, these can not be
defined for each module. The thinking is that all modules should be setup
the same to maintain consistancy. Of course, each user can decide what
settings they want for all of their modules. There is not much that you
can not control. Palettes can be defined within each module.
----------------------------------------------------------------------------
> I would like to select my own fonts, have draggable windows, etc.
----------------------------------------------------------------------------
Fonts and window options are set within each module definition. These
settings as well as many others can be defined and then compiled into a
module.
You can set the module fonts to anything or any size you want by
editing/creating the definition files and then compiling them with the
compiler. The requesters, menus and title font can be set with a tooltype.
Draggable windows is currently not an option. This will be added in a
future version if there is enough request for it.
----------------------------------------------------------------------------
> The .readme said new modules can be edited by users, but the examples
> are binaries. Please explain.
----------------------------------------------------------------------------
Modules are NOT editable, they are created by MSE-Compiler (not included
with the demo). Definition files, however, are simple text files. The
demo includes sample definition files in the definitions directory.